TrustRadius Insights
User-Friendly Interface: Many users have found the system to be user-friendly and easy to manage, with simple settings and management that …
Overview
What is HPE BladeSystem?
HPE BladeSystem is a brand of blade server, from Hewlett-Packard Enterprise. HPE blades include the ProLiant BL series and the ProLiant WS series.
Recent Reviews
Product Details
- About
- Tech Details
What is HPE BladeSystem?
HPE BladeSystem Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(25)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Pros
- Cons
User-Friendly Interface: Many users have found the system to be user-friendly and easy to manage, with simple settings and management that simplify tasks. They appreciate the intuitive design and straightforward controls that make it effortless for them to navigate through the system.
Scalability: Several reviewers have praised the scalability of the solution, noting that it allows for the easy expansion of resources and the ability to fit multiple servers into a standard 19-inch rack. This flexibility in scaling up or down provides users with the freedom to adapt their infrastructure according to their evolving needs.
High Degree of Redundancy: The high degree of redundancy provided by the system has been appreciated by users, as it ensures the reliability and availability of hardware resources. With redundant components and failover mechanisms in place, customers can rely on uninterrupted operations even in case of hardware failures.
Buggy Management Console: Some users have experienced bugs in the management console, which can be frustrating and impact their ability to efficiently manage the system. They have reported encountering issues with the functionality and reliability of the console.
Limited Configuration Methods: Users feel that the configuration methods are limited to only web GUI and SSH command line, which restricts their flexibility and may not cater to all user preferences. This limitation hampers their ability to configure the system according to their specific requirements.
Outdated Virtual Connect Web GUI: The virtual connect web GUI still uses flash, which is seen as somewhat dated by users who would prefer a more modern interface. They believe that an updated web GUI using newer technologies would enhance usability and provide a better user experience.
Attribute Ratings
Reviews
(1-3 of 3)Companies can't remove reviews or game the system. Here's why
HPE Blade System is used in our VDI and VSI environment with HPE VC as Network Module with more than 10 Blades everything is running with ESXi and virtual Server. The setup is stretched between 2 datacenters. For VDI, we are using Grphaiccards on top. With this, we are able to operate the whole internal IT.
- Very Flexible
- With Virtual Connect you have a very powerfull Network Module for Management
- Easy Maintenance
- Scale Up is not a problem
- It doesn't take that much rack space
- Long Boot Time (Perhaps in most HPE Servers)
- Fan Management, when you not using the whole Blade Enclosure make sure all Blades are on one site.
- Limitation in Hardware because of thermik
- Not exactly ROI but its very stable
- Powerful
HPE BladeSystem was a well known product in our company. Also HPE Apollo is not able to use Virtual Connect, what means that you have to connect every Apollo Server to the Network. That has a huge impact on the network site.
March 14, 2021
HPE BladeSystem: Used for Almost 10 Years
HPE BladeSystem is being used as our primary server platform for all production services in our organization. It has been employed since Gen1 and has been used for its ability to virtualize what used to be very manual cabling, networking, and server management. Blades come in a variety of configurations and capabilities to fit the business need. We're using BL360s in a c7000 chassis with FlexFabric 10Gbps ports for Ethernet and SAN. This is a basic configuration that allows us to run a dense VM environment with minimal external cabling and networking and complete remote management.
- Variety of server configurations
- Complete remotely managed server hardware, networking, connectivity, and monitoring.
- Repeatable configurations
- Configuration methods: Only Web GUI and SSH command line.
- Virtual Connect web GUI still uses flash :(
- Bay-to-server-to-card hardware "mapping" is kind of confusing at first.
- Less hardware management (racking, cabling, etc.).
- Less hardware (cabling, ports, switches, etc.)
- Remote server management (power on, networking, configuring, etc.)
We tested Cisco UCS in its early days, so this might be a bit of an old comparison, but UCS had the promise of being very configurable, with templates for everything and automatable for just about every task. However, even working with a Cisco engineer for weeks, we could not get a basic setup to work for us. Although there is a small learning curve with HPE BladeSystem, it has served us faithfully for almost 10 years.
September 27, 2017
BladeSystem provides user dense compute without compromise
HPE ProLiant Bladesystem is being used to support applications and virtualization across the entire organization. The blade infrastructure provided a very dense compute platform with flexibility to wire the system once and then move workloads between hosts easily.
- Increase the density of compute with 16 servers in 10U of rack space.
- Shares high-bandwidth uplinks to flexibly wire the fabric for the systems.
- Provides the ability to migrate workloads between physical hardware easily with server profiles.
- The small form factor of a blade server cannot accommodate expansion cards.
- Shared infrastructure, like the interconnects, means a larger fault domain.
- Firmware updates can be disruptive and administrators should pay close attention to firmware recipes and bundles to ensure compatibility between components.
- The number of ports required for connectivity to 16 physical server is reduced with BladeSystem, without compromising flexibility - so there is a 16x savings on the number of ports required on physical switching infrastructure.
- In-place upgrades to newer hardware are accommodated by virtualized MAC addresses and WWN's in the fabric of the BladeSystem.
- On a couple occasions, large scale outages have affected the environment because of an issue at the core of BladeSystem. Users should be aware of the fault domain caused by a single chassis and plan accordingly. Our issues were mitigated due to a second, separate chassis where we spread workloads.
BladeSystem provides a close experience to the UCS B-Series. UCS B-Series has a few capabilities within the network fabric that exceed what is capable on BladeSystem, but HPE has developed a lot of orchestration within HPE OneView to offer feature parity or even go beyond what is capable with UCS B-Series. The primary difference between the two is a compute centric (BladeSystem) versus a fabric centric (UCS) design. All administration is based around servers in BladeSystem versus the close ties to the fabric in UCS.